Skip to main content

Multidev Support Overview

Handoff to IT

  • Production Server Configurations

    • See: O:\MISGRP\Multidev\Implementation Documentation\Production Service Equipment Recommendations.msg
    • See: O:\MISGRP\Multidev\Implementation Documentation\Firewall Configuration Emails
    • Comments:
      • Production database and application server installation and setup needs to be completed.
      • Virtual servers have been setup in Hyper-V per the specifications provided by Multidev.

  • Service Maintenance

    • Server Startup See: O:\MISGRP\Multidev\Implementation Documentation\FW_ Daniels - Servers restart.msg See: O:\MISGRP\Multidev\Implementation Documentation\Multidev Server Restart.xlsx (updated from what was included in email)
    • Comments:
      • Server shutdown/startup procedures need to be proofed, tested, and proofed.
      • Based on experience with the test/lab server, it appears that some of the Multidev services need to be set to delayed start (they depend on the Interbase database, which may take some time to start) OR set as dependencies to pre-requisite services.

  • POS Installations

    • See: O:\MISGRP\Multidev\Implementation Documentation\POS installation guide.msg
    • Pole Displays See: O:\MISGRP\Multidev\Implementation Documentation\Pole Display Configuration.docx
    • Payment Terminals – UTG Installations and Shift4/Multidev configurations See: O:\MISGRP\Multidev\Shift-4\Shift4 and Multidev UTG Installation Instructions.docx This document is incomplete and further test environment work is required.
    • Switching lab to production
      • Pablo advises that a simple swap/edit on postagent.ini file will likely not achieve the desired result and could result in extended support issues.
    • Comments:
      • Further work on all POS workstations is needed to finalize the installation/configuration of pole displays.
      • Further work on all POS workstations is needed to finalize the installation/configuration of Shift4 UTG software and Multidev integration.

  • SF Installations

    • Switching lab to production
    • Comments:
      • Open SF installations.
      • Terminal Server access users.
      • More work is required to address printing issues:
        • Current environment:
          • Most all production/ERP printing is done from Universe.
          • Printers are installed and configured for use on the Universe server and through Universe configuration files.
          • The Universe Output Controller allows users to move and redirect output, including to email, on a per task basis.
          • Meaning that each user workstation has limited Universe/ERP production-based printing configurations.
        • New environment:
          • All printing is done through printers that are installed/accessed through Windows on the user’s workstation.
          • Many SF printing requirements/functions are addressed through “default” printing configuration, i.e., the user has fewer opportunities to redirect printing when the task is being done.
        • A general review of printers that are installed/available to each user’s workstation through Windows is required to help ease conversion and future use issues.
        • Special cases:

          • Ticket printers

          • Check printer

      • General review desktop ICON and program access.
      • Scan to Transfer Configuration See: O:\MISGRP\Multidev\Implementation Documentation\Scan to Transfer.docx
      • More documentation needed here required regarding licensing and *.mdv files at each workstation.
      • More documentation needed here required regarding identifying busy binary/.exe files at the server so that users can be called to close and/or force closed for the purposes of upgrades and updates.

  • PR Management

    • The PR Generator is a program that updates POS for various changes in SF/SV1020 database.
    • The list of updates that occur SF/SV1020 database and POS systems (SMC to POS) OUTSIDE OF THE PR GENERATOR is continually being updated. As of 10/30/23 see help desk ticket 28091144.
      • Employees
      • Transfers
      • Quantity on hand information
      • Purchase orders
      • Customer and repair updates made in SF/SV1020.
    • The list of EVERYTHING ELSE is still being documented:
      • New products
      • Price changes
      • PR Configurator Items (only key items listed)
        • Security process changes
        • Tender codes/configuration
        • Master cash
          • **Documentation needed from Multidev needed to address intra-PR Generator updates to master cash record when the primary workstation in a store goes down. Is a PR required, or can this PR configurator item be updated without a PR?
    • PR Generator runs as console application with a scheduled execution time – 3:00 AM
    • Multiple PR Generators can be run with different execution times, e.g., 3:00 AM and 3:00 PM
    • A new PR during the business day may cause confusion with users.
    • Comments:
      • Procedures and follow-up processes need to be put into place to review errors that are generated during the PR process.

  • Backups

    • More training and information is needed from Multidev regarding automated backups
      • Superform – security, field layouts, metadata
      • SV1020.STATS
      • SV1020 Continued to be monitored, managed by Art:

  • Employee Updates

    • Updates to EMPLOYEE either through SF or the import of a UKG file will be automatically distributed to store within approximately 10 minutes, or less.
    • Comments:
      • UKG file import process needs to be finalized.
        • Automated transfer of file from FTP location to local/network directory.
        • Scheduled task to apply newly received file.

  • Security

    • POS - See: O:\MISGRP\Multidev\Implementation Documentation\POS Security Configuration.docx
    • SF
      • Tools/Security Manager
      • System Settings/Security/Usage Security by Business Process
      • Comments:
        • This is a work in progress. More documentation to be provided.
    • Accounting – Two Separate Applications
      • Accounting Access Control – controls user’s access to the database for accounting purposes. See: O:\MISGRP\Multidev\Implementation Documentation\20131202 Chaindrive User Management.doc
      • Accounting-Security – controls user’s access to areas within the Accounting Application.

  • Metadata and Field Lists

    • More documentation to be created regarding metadata editing.
    • Pending response from Multidev regarding updates to Metadata editing Safe Mode.